Repository navigation
release v0.2.4 - #29
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release 0.2.4
Generated by the Release prep workflow. Merging this PR creates annotated tag
v0.2.4and runs the Release workflow: verify -> GitHub Release -> crates.io publish (Trusted Publishing OIDC, tokenless).Changelog
[0.2.4] - 2026-11-06
Changed
@deepseek-ai/[email protected], and both frozen contracts — the wire-parity surface and the launch contract — were re-baselined against it. The wire delta is additive: upstream now declares eight request methods while this crate still sends the same six, andsession/query,approval/request, anduser-question/askstay deliberately unwrapped, so a leading/in run input is still sent to the model as prompt text rather than executed as a native command.subagent.startedis emitted only for subagent-origin sessions (an ordinary fork therefore adds no tree edge), and a resumed session takes the initialized provider/model route instead of its stored selection, where a stored reasoning effort survives only when both match. The two added notification names reach the crate only through its unknown-method path.>= 24.9.0. The crate still installs, downloads, and versions nothing, so a caller below that bound sees the runtime's own engine failure rather than a crate error.